Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-33977 | SRG-NET-000076-DNS-000036 | SV-44430r1_rule | Medium |
Description |
---|
Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is being performed on the system, where an event occurred, when an event occurred, and by whom the event was triggered, in order to compile an accurate risk assessment. Logging the actions of specific events provides a means to investigate an attack, recognize resource utilization or capacity thresholds, or to simply identify an improperly configured DNS implementation. Without log records that aid in the establishment of where the event occurred, there is no traceability for forensic or analytical purposes. Without sufficient information establishing where the audit events occurred, investigation into the cause of events is severely hindered. |
STIG | Date |
---|---|
Domain Name System (DNS) Security Requirements Guide | 2012-10-24 |
Check Text ( C-41981r1_chk ) |
---|
Review the DNS system configuration to determine if it is configured to produce, capture and store log records which contain information to establish where events have occurred on the system. If the logging function is not configured to produce log records with information regarding where the event took place, this is a finding. |
Fix Text (F-37892r1_fix) |
---|
Configure the DNS server to produce log records that contain information that establishes where events have occurred. Additionally, configure the audit facility of the DNS system to provide information where events have occurred. |